Hello. I've been tasked with putting together some best practices for our Reporting Services 2008 R2/SharePoint 2010 integrated environment. A SharePoint site with Enterprise Site features enabled generates several types of document libraries -- among them Data Connections and a Reports Library (Documents, Images, Pages, and Reference Library are the others, just for context). - Is there a good reason to use the Report Library for Reporting Services reports (.rdl files)? The only difference I see between it and a regular document library is the ability to create a blank report (just an Excel file) from the Documents menu. - Similarly is there a good reason to use the Data Connections library to store our Reporting Services data sources (.rds files)? I feel like these repositories are meant for something else -- or that our configuration is lacking. Can someone clarify? Perhaps the underlying question is, is there a best practice for organizing Reporting Services reports and their dependency files within a SharePoint site (beyond merely separating reports, data sources and data sets)? Thank you.

Hi Bvy, Sorry for the delay. When we configure a report server to run in SharePoint integration mode, we can add any report server content types to a common document library. For a document library that owns report server content types, it has no differences with the report type library torwards Reporting Services features. So, it doesn't matter wheter we obtain a library by creating a report library or by adding report server content types to a document library. References: How to: Add Report Server Content Types to a Library Overview of Reporting Services and SharePoint Technology Integration Regards, Mike Yin TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Mike Yin TechNet Community Support